Program Instruction Changes

futarchy

initialize_dao / update_dao — new DAO invariant checks reject zero values

Three new invariant checks are enforced. Any initialize_dao or update_dao call that sets any of these to 0 will now fail:

• min_base_futarchic_liquidity > 0
• min_quote_futarchic_liquidity > 0
• twap_max_observation_change_per_update > 0

launch_proposal — rejects zero reserves

New require_gt! checks on base_to_lp and quote_to_lp. A proposal whose spot pool has insufficient reserves (resulting in zero after halving) will now fail to launch.

provide_liquidity — rejects zero base amount

New require_gt!(max_base_amount, 0) check. Calls with max_base_amount = 0 will now fail.

v06_launchpad

complete_launch — DAO created with non-zero min futarchic liquidity

min_quote_futarchic_liquidity and min_base_futarchic_liquidity changed from 0 to 1. DAOs created by this instruction will have stricter invariants than before.

v07_launchpad

complete_launch — same change as v06_launchpad

min_quote_futarchic_liquidity and min_base_futarchic_liquidity changed from 0 to 1.

Additional notes

• PDA seed byte strings extracted into named constants — identical bytes, no on-chain effect
• Dao account boxed in CollectFees, UpdateDao, WithdrawLiquidity — Rust memory optimization only, no wire format or IDL change
• Arbitrage early-exit optimization — saves compute, no behavioral change for callers
• finalize_proposal safe cast (as i16 → i16::try_from()) — unreachable in practice due to MAX_PASS_THRESHOLD_BPS = 1_000 invariant